Ballistic estimation of vehicle data

ABSTRACT

Embodiments of the disclosure provide systems and methods for ballistically estimating vehicle data. The system may include a communication interface configured to receive a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point. The system may further include at least one processor. The at least one processor may be configured to compute a first set of vehicle data based on the first vehicle measurement, and estimate a second set of vehicle data for the second time point based on the first set of vehicle data and a model. The at least one processor may be further configured to compute a third set of vehicle data based on the second vehicle measurement. The at least one processor may also be configured to update the model based on a comparison between the second set of vehicle data and the third set of vehicle data. The system may also include a storage configured to store the first and second vehicle measurements, the model, and the first, second, and third sets of vehicle data.

TECHNICAL FIELD

The present disclosure relates to systems and methods for estimating vehicle data, and more particularly to, systems and methods for ballistically estimating vehicle data using a model that is adaptively updated using a difference between the calculated data and the estimated data.

BACKGROUND

Autonomous driving technology relies on large scale computation of vehicle data. For example, autonomous driving vehicles need to capture and process various vehicle data to obtain the vehicle data necessary to perform functions such as positioning, ambience recognition, decision making and control. For example, a vehicle may be equipped with multiple integrated sensors such as a Light Detection And Ranging (LiDAR) LiDAR, a Global Positioning System (GPS) receiver, one or more Inertial Measurement Unit (IMU) sensors, RADAR sensors, Sonic and Ultra Sonic sensors, and one or more cameras, to capture data such as images/videos, point clouds, vehicle pose information, etc.

Because autonomous driving vehicles often have to make decisions in real-time. Therefore, it is often critical to have a result of computation ready as soon as possible. However, this is difficult due to computational limitations. For example, processing a video feed from vehicle cameras could take a relatively long time (e.g., 200-300 ms), but the decision has to be made in less than 100 ms. To improve the data processing speed, one approach is to use a powerful computing unit. However, this approach is usually very costly solution, and also has limited scalability. Another approach is to use a less accurate, but faster processing algorithm to identify the next state of the environment. For example, one may use Kalman filter or recurrent neural networks to predict the behavior of the system before the computation is complete. However, this approach is usually computationally expensive and requires a lot of prior knowledge to behave properly. If the prior knowledge is imprecise, all future predictions become erroneous, which leads to unexpected behavior. The approach may also suffer from limited statistical performance (e.g., higher error rate, lower precision, etc.), which might be problematic under certain circumstances. Therefore, an improved system and method for estimating vehicle data fast and accurately is needed.

Embodiments of the disclosure address the above problems by systems and methods for ballistically estimating vehicle data using a model that is adaptively updated using a difference between the calculated data and the estimated data.

SUMMARY

Embodiments of the disclosure provide a system for ballistically estimating vehicle data. The system may include a communication interface configured to receive a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point. The system may further include at least one processor. The at least one processor may be configured to compute a first set of vehicle data based on the first vehicle measurement, and estimate a second set of vehicle data for the second time point based on the first set of vehicle data and a model. The at least one processor may be further configured to compute a third set of vehicle data based on the second vehicle measurement. The at least one processor may also be configured to update the model based on a comparison between the second set of vehicle data and the third set of vehicle data. The system may also include a storage configured to store the first and second vehicle measurements, the model, and the first, second, and third sets of vehicle data.

Embodiments of the disclosure also provide a method for ballistically estimating vehicle data. The method may include receiving, via a communication interface, a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point. The method may further include computing, by at least one processor, a first set of vehicle data based on the first vehicle measurement, and estimating, by the at least one processor, a second set of vehicle data for the second time point based on the first set of vehicle data and a model. The method may yet further include computing, by the at least one processor, a third set of vehicle data based on the second vehicle measurement. The method may also include updating, by the at least one processor, the model based on a comparison between the second set of vehicle data and the third set of vehicle data.

Embodiments of the disclosure further provide a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, causes the one or more processors to perform a method for ballistically estimating vehicle data. The method may include receiving a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point. The method may further include computing a first set of vehicle data based on the first vehicle measurement, and estimating a second set of vehicle data for the second time point based on the first set of vehicle data and a model. The method may yet further include computing a third set of vehicle data based on the second vehicle measurement. The method may also include updating the model based on a comparison between the second set of vehicle data and the third set of vehicle data.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic diagram of an exemplary vehicle equipped with sensors, according to embodiments of the disclosure.

FIG. 2 illustrates a block diagram of an exemplary server for ballistically estimating vehicle data, according to embodiments of the disclosure.

FIG. 3 illustrates a flowchart of an exemplary method for ballistically estimating vehicle data, according to embodiments of the disclosure.

FIG. 4 illustrates an exemplary vehicle data estimation process, according to embodiments of the disclosure.

FIG. 5 illustrates an exemplary vehicle data estimation process based on a video feed, according to embodiments of the disclosure.

DETAILED DESCRIPTION

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 illustrates a schematic diagram of an exemplary vehicle 100 having a plurality of sensors 140 and 150, according to embodiments of the disclosure. Consistent with some embodiments, vehicle 100 may be configured to be operated by an operator occupying the vehicle, remotely controlled, and/or autonomous. It is contemplated that vehicle 100 may be an electric vehicle, a fuel cell vehicle, a hybrid vehicle, or a conventional internal combustion engine vehicle. Vehicle 100 may have a body 110 and at least one wheel 120. Body 110 may be any body style, such as a sports vehicle, a coupe, a sedan, a pick-up truck, a station wagon, a sports utility vehicle (SUV), a minivan, or a conversion van. In some embodiments, vehicle 100 may include a pair of front wheels and a pair of rear wheels, as illustrated in FIG. 1. However, it is contemplated that vehicle 100 may have more or less wheels or equivalent structures that enable vehicle 100 to move around. Vehicle 100 may be configured to be all wheel drive (AWD), front wheel drive (FWR), or rear wheel drive (RWD).

As illustrated in FIG. 1, vehicle 100 may be equipped with sensor 140 mounted to body 110 via a mounting structure 130. Mounting structure 130 may be an electro-mechanical device installed or otherwise attached to body 110 of vehicle 100. In some embodiments, mounting structure 130 may use screws, adhesives, or another mounting mechanism. Vehicle 100 may be additionally equipped with sensor 150 inside or outside body 110 using any suitable mounting mechanisms. It is contemplated that the manners in which sensor 140 or 150 can be equipped on vehicle 100 are not limited by the example shown in FIG. 1, and may be modified depending on the types of sensors of 140/150 and/or vehicle 100 to achieve desirable sensing performance.

In some embodiments, sensors 140 and 150 may be configured to capture data as vehicle 100 travels along a trajectory. Consistent with the present disclosure, sensor 140 may be a camera configured to take pictures or videos of the surrounding. For example, the camera may be a monocular or binocular camera. In some embodiments, sensor 140 may also be a LiDAR configured to scan the surrounding and acquire point clouds. LiDAR measures distance to a target by illuminating the target with pulsed laser light and measuring the reflected pulses with a sensor. Differences in laser return times and wavelengths can then be used to make digital 3-D representations of the target. The light used for LiDAR scan may be ultraviolet, visible, or near infrared. In some embodiments, a LiDAR may capture a point cloud. Point cloud data may contain a set of data points on the external surfaces of objects around it. A point cloud can be processed to construct a 3-D model of the objects. In some embodiments, sensor 140 may also be other types of sensors such as RADAR sensors, Sonic and Ultra Sonic sensors.

As vehicle 100 travels along the trajectory, sensor 140 may continuously capture data. Each set of scene data captured at a certain time point is known as a data frame. For example, sensor 140 may record a video consisting of multiple image frames captured at multiple time points. Sensor 140 may also capture point cloud frames at the multiple time points. The data frames may be transmitted to a server 160 in real-time (e.g., by streaming).

As illustrated in FIG. 1, vehicle 100 may be additionally equipped with sensor 150. In some embodiments, sensor 150 may include positioning sensors, such as a GPS receiver and one or more IMU sensors. By combining the GPS receiver and the IMU sensor, sensor 150 can provide real-time pose information of vehicle 100 as it travels, including the positions and orientations (e.g., Euler angles) of vehicle 100 at each time point. In some embodiments, sensor 150 may take vehicle measurements such as vehicle pose information, at the same time points where sensor 140 captures the image frames.

Consistent with the present disclosure, sensors 140 and 150 may communicate with server 160. In some embodiments, server 160 may be a local physical server, a cloud server (as illustrated in FIG. 1), a virtual server, a distributed server, or any other suitable computing device. Server 160 may communicate with sensors 140, 150, and/or other components of vehicle 100 via a network, such as a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, a satellite communication network, and/or a local or short-range wireless network (e.g., Bluetooth™).

Consistent with the present disclosure, server 160 may be responsible for estimating vehicle data based on the sensor measurements. In some embodiments, server 160 may include at least two processing units to process the sensor measurements in parallel. At least one processor unit is configured to calculate vehicle data based on the sensor measurements using a regular approach, e.g., to identify vehicle velocity, acceleration, heading, color, maker, etc. from image frames of a video feed captured by sensor 140. Another processor unit is configured to estimate vehicle data from the sensor measurements using an expedited approach. In some embodiments, the expedited approach uses a prediction model trained for predicting vehicle data faster than the regular approach. For example, the processor unit may predict vehicle data based on vehicle data at previous time points and a prediction model specifying the behavior of vehicle data among different image frames. In some embodiments, the expedited approach can predict vehicle data in real-time.

In some embodiments, the prediction model may be a learning network defined by multiple parameters. Because the prediction model predicts future vehicle data based on existing vehicle data, errors caused by the model may be accumulated over time. To ensure the accuracy of prediction model and reduce the accumulated error, the model may be updated using vehicle data computed through the regular approach. In some embodiments, the computed vehicle data (through the regular approach) and the estimated vehicle data (through the expedited approach) may be compared. For example, a difference between the two may be feedback to update the parameters of the prediction model.

Although the present disclosure describes estimation of vehicle data based on sensor measurements, it is contemplated that the disclosed systems and methods may be adapted to estimate other data unrelated to sensor measurements or unrelated to a vehicle. In addition, the disclosed systems and methods may also be adapted to perform operations other than data estimation.

For example, FIG. 2 illustrates a block diagram of an exemplary server 160 for ballistically estimating vehicle data, according to embodiments of the disclosure. Consistent with the present disclosure, server 160 may receive measurements from sensor 140 and sensor 150. Based on the sensor measurements, server 160 may estimate vehicle data through a dual processor approach.

In some embodiments, as shown in FIG. 2, server 160 may include a communication interface 202, a processor 204, a memory 206, and a storage 208. In some embodiments, server 160 may have different modules in a single device, such as an integrated circuit (IC) chip (implemented as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA)), or separate devices with dedicated functions. In some embodiments, one or more components of server 160 may be located in a cloud, or may be alternatively in a single location (such as inside vehicle 100 or a mobile device) or distributed locations. Components of server 160 may be in an integrated device, or distributed at different locations but communicate with each other through a network (not shown).

Communication interface 202 may send data to and receive data from components such as sensors 140 and 150 via communication cables, a Wireless Local Area Network (WLAN), a Wide Area Network (WAN), wireless networks such as radio waves, a cellular network, and/or a local or short-range wireless network (e.g., Bluetooth™), or other communication methods. In some embodiments, communication interface 202 can be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection. As another example, communication interface 202 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links can also be implemented by communication interface 202. In such an implementation, communication interface 202 can send and receive electrical, electromagnetic or optical signals that carry digital data streams representing various types of information via a network.

Consistent with some embodiments, communication interface 202 may receive data such as a video feed 203 captured by sensor 140. Communication interface 202 may further provide the received data to storage 208 for storage or to processor 204 for processing.

Processor 204 may include any appropriate type of general-purpose or special-purpose microprocessor, digital signal processor, or microcontroller. Processor 204 may be configured as a separate processor module dedicated to estimating vehicle data. Alternatively, processor 204 may be configured as a shared processor module for performing other functions unrelated to color point cloud generation.

As shown in FIG. 2, processor 204 may include multiple modules, such as a first processing unit 210, a second processing unit 212, and a model update unit 214, and the like. These modules (and any corresponding sub-modules or sub-units) can be hardware units (e.g., portions of an integrated circuit) of processor 204 designed for use with other components or software units implemented by processor 204 through executing at least part of a program. The program may be stored on a computer-readable medium, and when executed by processor 204, it may perform one or more functions. Although FIG. 2 shows units 210-214 all within one processor 204, it is contemplated that these units may be distributed among multiple processors located near or remotely with each other.

First processing unit 210 may be configured to compute vehicle data based on sensor measurements received from sensors 140 and 150. The computation of first processing unit 210 provides results with very high accuracy but may be slow. For example, the computation result for time point t₁ may not be available until time point t₅. Therefore, the computation of first processor unit 210 is not real-time.

In some embodiments, first processing unit 210 may be further configured to compute a model for the current behavior of the results, and share the model with second processor unit 212. In some embodiments, the model may be a learning network defined by multiple model parameters.

Second processing unit 212 may be configured to estimate vehicle data for the next time points using the model based on the vehicle data for previous time points. For example, the vehicle data V(t_(k)) at time point t_(k) may be estimated using model F as V(t_(k))=F(V(t_(k-1)), a, b, c) where V(t_(k-1)) is the vehicle data at time point t_(k-1) and a, b, and c are model parameters. Second processing unit 212 is not necessarily connected to the external sensors (i.e. sensors 140 and 150), but only tries to predict the results based on what first processing unit 210 shared. Because data processing using the model may involve much less computations, the estimation performed by second processing unit 212 may be extremely fast. Accordingly, the computation result for time point t_(k) may be available in real-time, e.g., shortly after time point t_(k).

Model update unit 214 may be configured to update the model. In some embodiments, the model may be updated upon the next computation result from first processing unit 210 becomes available. In some embodiments, the model may be updated based a difference between the computed result by first processing unit 210 and the corresponding estimated result by second processing unit 214. For example, once calculated vehicle data for time point t₂ VV(t₂) is available at time point t₅, its difference from the estimated vehicle data for time point t₂ V(t₂)|VV(t₂)−V(t₂)| may be calculated. The model F may be updated based on |VV(t₂)−V(t₂)|. In some embodiments, the model parameters a, b, and c may be updated. The updated model may replace the model being used by second processing unit 212.

Memory 206 and storage 208 may include any appropriate type of mass storage provided to store any type of information that processor 204 may need to operate. Memory 206 and storage 208 may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium including, but not limited to, a ROM, a flash memory, a dynamic RAM, and a static RAM. Memory 206 and/or storage 208 may be configured to store one or more computer programs that may be executed by processor 204 to perform vehicle data estimation functions disclosed herein. For example, memory 206 and/or storage 208 may be configured to store program(s) that may be executed by processor 204 to estimate vehicle data in real-time using a model that is adaptively updated using computed vehicle data.

Memory 206 and/or storage 208 may be further configured to store information and data used by processor 204. For instance, memory 206 and/or storage 208 may be configured to store the various types of data (e.g., image frames, pose information, etc.) captured by sensors 140 and 150 and the high-definition map. Memory 206 and/or storage 208 may also store intermediate data such as the computed data by first processing unit 210, estimated data by second processing unit 212, and the prediction model and its parameters, etc. The various types of data may be stored permanently, removed periodically, or disregarded immediately after each frame of data is processed.

FIG. 3 illustrates a flowchart of an exemplary method 300 for ballistically estimating vehicle data, according to embodiments of the disclosure. In some embodiments, method 300 may be implemented by server 160 that includes, among other things, processor 204. However, method 300 is not limited to that exemplary embodiment. Method 300 may include steps S302-S318 as described below. It is to be appreciated that some of the steps may be optional to perform the disclosure provided herein. Further, some of the steps may be performed simultaneously, or in a different order than shown in FIG. 3.

In step S302, vehicle measurement M₁ may be received at time point t₁. In some embodiments, vehicle measurement M₁ may be image data captured by sensor 140 or vehicle pose data acquired by sensor 150. In step S304, first processing unit 210 may compute a set of vehicle data VV₁ using the vehicle measurement M₁. For example, first processing unit 210 may identify vehicle velocity, acceleration, heading, color, and maker, etc. based on the image data received from sensor 140.

In step S306, second processing unit 212 may estimate a set of vehicle data V₂ corresponding to time point t₂. V₂ may be estimated using model F provided by first processing unit 210. For example, V₂=F(VV₁, a, b, c). In step S308, vehicle measurement M₂ may be received at time point t₂. Similar to M₁, vehicle measurement M₂ may be image data captured by sensor 140 or vehicle pose data acquired by sensor 150.

In step S310, first processing unit 210 may compute a set of vehicle data VV₂ using the vehicle measurement M₂. In some embodiments, the computation may involve a significant number of computations. Therefore, the computation result of VV₂ may not be available until much later than time point t₂. For example, VV₂ may be available at time point t₅.

In step S312, model update unit 214 may compare VV₂ with V₂, upon VV₂'s availability. In some embodiments, a difference between VV₂ and V₂ may be calculated, e.g., as |VV₂−V₂|. It is contemplated that a second order difference such as ∥VV(t₂)−V(t₂)∥ or an even higher order difference may be calculated instead. The difference indicates an accumulated error in the estimated vehicle data.

In step S314, the difference is compared with a predetermined threshold. If the difference (i.e., the error) is sufficiently large (S314: yes), method 300 proceeds to step S316 to update the model F. In some embodiments, the model parameters, such as a, b, and c of model F, may be updated using the difference determined in step S312. Various algorithms may be used to update the model parameters, such as stochastic gradient descent (also known as a “hill-climbing” algorithm). The updated model F may be used for estimation of subsequent vehicle data. Accordingly, the accumulated estimated error is adaptively corrected every few time points.

If the difference (i.e., the error) is below the threshold (S314: no), method 300 proceeds to step S318 to substitute the estimated vehicle data V₂ with the more accurate, calculated data V₂ for time point t₂. In some embodiments, vehicle data V₃, V₄, and V₅, etc. may be re-calculated using model F based on the more accurate V₂. Step S318 may be optional.

FIG. 4 illustrates an exemplary vehicle data estimation process 400, according to embodiments of the disclosure. Process 400 estimates vehicle velocity and acceleration data based on position measurements. For example, vehicle positions may be acquired by sensor 150 and received by server 160. As shown by FIG. 4, process 400 uses dual processing modules: a slow module 410 and a fast module 420.

Slow module 410 calculates vehicle velocity and acceleration data according to a function F_(i)(

). For example, slow module 410 may use the following Equation (1):

$\begin{matrix} \left\{ {\begin{matrix} {v_{k} = {v_{\{{k - 1}\}} + {\sin \; k} + {\log \left( {k + 1} \right)}}} \\ {S_{k} = {S_{\{{k - 1}\}} + v_{\{{k - 1}\}}}} \end{matrix},} \right. & (1) \end{matrix}$

where v_(k) represents velocity at time k, and S_(k) is the position at time k. In some embodiments, slow module 410 computes vehicle data every five time units based on the received position data.

Fast module 420 estimates vehicle velocity and acceleration data every time unit (i.e., in real-time) using a simple single layer perceptron network. For example, fast module 429 may use an approximation form to function F_(i)(

) used by slow module 410:

{circumflex over (F)} _(j)=(F _(i−1) ,{circumflex over (F)} _(j-1) ,A _(i−1))=A _(i−1)·[F _(i−1) ,{circumflex over (F)} _(j-1)]^(T)  (2),

where A_(i−1) is a set of parameter approximations updated at time i−1, F_(i−1) is the previous true result of the computation, {circumflex over (F)}_(i−1) is the previous approximation result, and i, j are the indices of the current slow and fast outputs respectively. There may be other parameters, such as current index j and partial inputs from the real world.

The parameters A are defined by slow module 410. In some embodiments, the model selection may be performed from a fix pool of polynomial and trigonometric functions. The model may be trained by slow module 410 based on previously observed points using stochastic gradient descent algorithms. For example, after a certain number of iterations (e.g., 100 iterations), {circumflex over (F)}_(j) converges to a model with four time parameters: [t{circumflex over ( )}2, t{circumflex over ( )}3, tan (t)].

In order for fast model 420 to maintain its computation accuracy, its parameters may be periodically updated. A residual error between the two functions may be calculated. In some embodiments, the residual error may be the square of the output differences, which can be written as ε_(i,j)=F_(i) ²+{circumflex over (F)}_(j) ²−2F_(i){circumflex over (F)}_(j). In some embodiments, the model parameters may be updated at every iteration i, which is the rate of the slow model 410 (i.e., every five time units). For example, parameters A may be updated using Equation (3) as follows:

A _(i+1) =A _(i)−γ∇ε_(i)·(A _(i))  (3).

If γ is small enough, ε_(i)·≥ε_(i+1)· may be achieved, which means that the residual error will be smaller after each update. The choice of γ affects how fast the equations converge and how accurate is the convergence. If γ is very big, the algorithm either converges immediately to a sub-optimal solution, or never converges at all (oscillates between bad solutions). If γ is very small, the algorithm converges, but may take many iterations, which may slow down process 400.

In some embodiments, assuming that function ε is convex and ∇ε is Lipschitz, convergence may be guaranteed by setting the γ as:

$\begin{matrix} {\gamma_{i} = {\frac{\left( {A_{i} - A_{i - 1}} \right)^{T}\left( {{\nabla ɛ_{i}} - {\nabla ɛ_{i - 1}}} \right)}{{{{\nabla ɛ_{i}} - {\nabla ɛ_{i - 1}}}}^{2}}.}} & (4) \end{matrix}$

Although a “hill-climbing” algorithm is described above as an example for updating the model parameters, it is contemplated that other gradient descent algorithms may be implemented as well. In addition, although model F is described above as a collection of linear equations, it is contemplated that other more sophisticated prediction models may be used by fast module 420. In some embodiments, the model may be a learning network, such as a neural network.

FIG. 5 illustrates an exemplary vehicle data estimation process 500 based on a video feed, according to embodiments of the disclosure. As shown in FIG. 5, vehicle 510 may travel along a trajectory 512. A camera 520 equipped on another vehicle (not shown) may capture a video of vehicle 510 as it travels along trajectory 512. The video may contain image frames captured at a set of time points. Typically, a set time interval is used between every two time points. For example, a new image frame may be captured every 1 ms, 2 ms, or the like. Vehicle 510 is at a different position corresponding to each time point when a new image frame is captured. Accordingly, each image frame can be associated with a vehicle position.

Process 500 may process the image frames of the video using a dual processor system to determine a number of vehicle data, such as vehicle 510's location, heading, velocity, color, shape, maker, etc. For example, process 500 may use processing unit 1 and processing unit 2. Processing unit 1 may be first processing unit 210 and processing unit 2 may be second processing unit 212, as described in connection with FIG. 2. For example, an image frame 530 captured at time point t₁ may be processed by processing unit 1 to determine vehicle data 540. In some embodiments, processing unit 1 may use image segmentation, image recognition, and other image processing methods to obtain vehicle data 540 from image frame 530. Image processing, particularly when the video feed is high-resolution, may require significant processing time. Accordingly, processing unit 1 may provide results in a slow, non-realtime fashion.

Processing unit 2 then estimates the next set of vehicle data 542′ (for time point t₂) based on vehicle data 540 using a predication model provided by processing unit 1. The model simplifies the computation by using existing knowledge by processing unit 1. In some embodiments, the model predicts where the vehicle 510 is going to be next based on given velocity, heading, and position. For example, the next position is previous position+velocity, and the next velocity is current velocity+acceleration. The model predicts the color of vehicle 510 based on its color at the previous time point and a determination if the vehicle is entering a shaded area. The model can assume that the shape and make of vehicle 510 should not change. Accordingly, the computation by processing unit 2 may be extremely fast.

Processing unit 2 does not consider the video input in its estimation, but only the vehicle data for previous time point(s). For example, processing unit 2 may continue to estimate the next set of vehicle data 544′ (for time point t₃) using the predication model and vehicle data 542′.

In parallel with the processing by processing unit 2, processing unit 1 continues to process the video feed in the slower fashion. For example, processing unit 1 may process an image frame 532 captured at time point t₂ to determine vehicle data 542. Vehicle data 542 may not be available in real-time, but rather a few time points later, such as at time point t₅. If the prediction model is accurate, estimated vehicle data 542′ may be sufficiently close to vehicle data 542. However, the model, being an approximation of the process performed by processing unit 1, typically contains an estimation error.

In order to correct that error, the prediction model used by processing unit 2 may be periodically updated using the accurate result. For example, vehicle data 542 and 542′ may be compared, and a difference between the two may be calculated. The difference may be used to update parameters of the prediction model used by processing unit 2. Accordingly, processing unit 2 may use the updated model to predict the vehicle data for subsequent time points.

Another aspect of the disclosure is directed to a non-transitory computer-readable medium storing instructions which, when executed, cause one or more processors to perform the methods, as discussed above. The computer-readable medium may include volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other types of computer-readable medium or computer-readable storage devices. For example, the computer-readable medium may be the storage device or the memory module having the computer instructions stored thereon, as disclosed. In some embodiments, the computer-readable medium may be a disc or a flash drive having the computer instructions stored thereon.

It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed system and related methods. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed system and related methods.

It is intended that the specification and examples be considered as exemplary only, with a true scope being indicated by the following claims and their equivalents. 

What is claimed is:
 1. A system for ballistically estimating vehicle data, comprising: a communication interface configured to receive a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point; at least one processor, configured to: compute a first set of vehicle data based on the first vehicle measurement; estimate a second set of vehicle data for the second time point based on the first set of vehicle data and a model; compute a third set of vehicle data based on the second vehicle measurement; and update the model based on a comparison between the second set of vehicle data and the third set of vehicle data; and a storage configured to store the first and second vehicle measurements, the model, and the first, second, and third sets of vehicle data.
 2. The system of claim 1, wherein the first and second vehicle measurements are image frames of a video feed captured by a sensor corresponding to the first time point and the second time point, respectively.
 3. The system of claim 2, wherein the sensor is a camera or a LiDAR.
 4. The system of claim 1, wherein the model is a learning network defined by a plurality of model parameters.
 5. The system of claim 4, wherein to update the model, the at least one processor is configured to update the plurality of model parameters.
 6. The system of claim 1, wherein the model is configured to estimate the second set of vehicle data by modifying the first set of vehicle data based on movement characteristics of a vehicle.
 7. The system of claim 6, wherein the movement characteristics include a position, a velocity, an acceleration, or a direction of the vehicle.
 8. The system of claim 1, wherein the model is updated using a stochastic gradient descent method.
 9. The system of claim 1, wherein the model is updated to reduce a difference between the second set of vehicle data and the third set of vehicle data.
 10. The system of claim 1, wherein the at least one processor includes a first processor configured to compute the first and third sets of vehicle data, and a second processor configured to estimate the second set of vehicle data.
 11. A method for ballistically estimating vehicle data, comprising: receiving, via a communication interface, a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point; computing, by at least one processor, a first set of vehicle data based on the first vehicle measurement; estimating, by the at least one processor, a second set of vehicle data for the second time point based on the first set of vehicle data and a model; computing, by the at least one processor, a third set of vehicle data based on the second vehicle measurement; and updating, by the at least one processor, the model based on a comparison between the second set of vehicle data and the third set of vehicle data.
 12. The method of claim 11, wherein the first and second vehicle measurements are image frames of a video feed captured by a sensor corresponding to the first time point and the second time point, respectively.
 13. The method of claim 11, wherein the model is a learning network defined by a plurality of model parameters.
 14. The method of claim 13, wherein updating the model includes updating the plurality of model parameters.
 15. The method of claim 11, further comprising estimating the second set of vehicle data by modifying the first set of vehicle data based on movement characteristics of a vehicle.
 16. The method of claim 15, wherein the movement characteristics include a position, a velocity, an acceleration, or a direction of the vehicle.
 17. The method of claim 11, wherein the model is updated using a stochastic gradient descent method.
 18. The method of claim 11, wherein the model is updated to reduce a difference between the second set of vehicle data and the third set of vehicle data.
 19. A non-transitory computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by at least one processor, performs a method for ballistically estimating vehicle data, comprising: receiving a first vehicle measurement taken at a first time point and a second vehicle measurement taken at a second time point; computing a first set of vehicle data based on the first vehicle measurement; estimating a second set of vehicle data for the second time point based on the first set of vehicle data and a model; computing a third set of vehicle data based on the second vehicle measurement; and updating the model based on a comparison between the second set of vehicle data and the third set of vehicle data.
 20. The non-transitory computer-readable medium of claim 19, wherein the first and second vehicle measurements are image frames of a video feed captured by a sensor corresponding to the first time point and the second time point, respectively. 